-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification about leftover change #10
Conversation
It an add other outputs for other reasons too, not just change. |
Also that line should have "PaymentDetails" changed to "PaymentRequest". We took out PaymentDetails. |
I see... In that case how about something like: Creates and signs a transaction that satisfy (pay in full) PaymentRequest.outputs. It may add additional outputs if needed. |
That makes sense. Again, "PaymentDetails" should be "PaymentRequest". |
yes - comment fixed |
Merged. Another relevant comment, though: It's actually unclear what the order of the outputs should be. Inside MB, we sort the outputs for increased privacy. This means the outputs are NOT returned in the same order. Perhaps we should clarify whether they should or should not be in the same order. |
Clarification would be good. It is technically possible to satisfy 2 payment requests with 1 transaction (and send that transaction to 2 different servers). Both are gonna find their inputs in it, but it is not possible for both to get the ordering they expected. // though... I have no idea why anyone would do something like that. :D |
deleting this branch. |
on output ordering, i created a new PR: #11 |
Added clarification about creating extra outputs and not just the ones requested.
// Just clarifying that having more outputs than the requested ones is OK.
// ...It is OK, isn't it?